System and method for achieving accelerated throughput

ABSTRACT

Systems and methods for transporting data between two endpoints over an encoded channel are disclosed. Data transmission units (data units) from the source network are received at an encoding component logically located between the endpoints. These first data units are subdivided into second data units and are transmitted to the destination network over the transport network. Also transmitted are encoded or extra second data units that allow the original first data units to be recreated even if some of the second data units are lost. These encoded second data units may be merely copies of the second data units transmitted, parity second data units, or second data units which have been encoded using erasure correcting coding. At the receiving endpoint, the second data units are received and are used to recreate the original first data units.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application No.12/193,345, filed Aug. 18, 2008, which is a continuation-in-part of U.S.patent application No. 10/912,200, filed Aug. 6, 2004, now U.S. Pat. No.7,742,501, all of which are hereby incorporated by reference in theirentirety.

FIELD OF THE INVENTION

The present invention relates to communication data networks. Morespecifically, the present invention relates to systems and methods forincreasing the throughput of data transmissions through a transportnetwork as seen from the edge of the transport network.

BACKGROUND OF THE INVENTION

Most, if not all, transport networks are packet based networks thatbreak up data streams into smaller packets of data which are thentransmitted from a first source network, or endpoint, to a thirddestination network, or endpoint, via a second transport network.However, due to congestion and other network limitations, not allpackets successfully arrive at the destination network. What matters tothe source and end destination networks is the performance of thetransport network. The transport network must, from the point of view ofthe applications at the end networks, ideally be perfect with no lostpackets. However, it would be preferred if such performance could be hadfor a price lower than the usual costs of leasing high performancetransport networks.

Accordingly, there is a need for systems and methods, which can be usedwith low cost communications transport networks to provide end networkapplications with a high performance view of the transport network.

Approaches have been tried to address the above situation. In oneapproach, custom protocol stacks are installed at the endpoints toimprove the response to loss and latency. However, this approachrequires that both end networks communicate according to the same customprotocol, which generally requires extensive reprogramming.

Another approach uses network elements that intercept standard protocolsand send protocol responses on behalf of a far-end element. Customprotocols are then used between the intercepting network elements. Thisapproach is limited to TCP/IP applications and adds complexity,especially in regards to troubleshooting network problems.

SUMMARY OF THE INVENTION

In a first aspect, there is provided a method of accelerating datacommunications over an unreliable network. The method comprisesproviding encoding components associated with each of two endpoints to acommunication. An encoded channel between the respective encodingcomponents is then established for a communication session between theendpoints. A data packet related to the communication session is thenintercepted at one of the encoding components. The data packet issegmented and marked to provide encoded data segments for transmissionto the other of the encoding components. The encoded data segments andat least one extra segment are then transmitted to the other of theencoding components over the encoded channel, where they are decoded andreassembled to recreate the data packet. The reassembled data packet isthen transmitted from the other of the encoding components to itsrespective endpoint. The encoded channel can be torn down if no furtherpackets are transmitted within a predetermined timeout period.

According to an embodiment, establishing the encoded channel cancomprise detecting a message originating from one of the two endpointsand destined to the other of the two endpoints; storing informationuniquely identifying the communication session; detecting a reply to themessage, and matching it to the previously stored informationidentifying the communication session; intercepting the reply; markingthe reply to indicate that the endpoint replying to the message isenabled to segment and encode data packets according to a protocol knownto both encoding components; forwarding the marked reply to the endpointoriginating the message; and exchanging control messages to establish anencoded channel between the encoding components.

According to another embodiment, establishing the encoded channelcomprises detecting a message originating from one of the two endpointsand destined to the other of the two endpoints; storing informationuniquely identifying the communication session; detecting a reply to themessage, and matching it to previously stored information identifyingthe communication session; intercepting the reply prior to delivery tothe endpoint originating the message; determining if the reply has beenmarked to indicate that the endpoint replying to the message is enabledto segment and encode data packets according to a protocol known to bothencoding components; and transmitting control messages to establish anencoded channel between the encoding components. Marking the reply cancomprise setting an option in an IP header, or setting an identificationfield to a known value.

In yet another embodiment, establishing the encoded channel comprisesdetecting control messages within one communication session thatestablish a related communication between the two endpoints according toa known protocol, the control messages including an identification ofthe related communication sessions's originating and destination ports;and creating an encoded channel in response to the detected controlmessages. Intercepting the control messages can, for example, compriseapplying deep packet analysis to the control message. This embodimentcan be used, for example, for RTSP and H.323 communications.

Segmenting and packaging the data packet can comprise segmenting thedata packet into data segments in accordance with a predeterminedencoding rate, or segmenting the data packet into data segments inaccordance with a dynamically adjusted encoding rate. The dynamicallyadjusted encoding rate can be determined by monitoring loss rates foreach of a plurality of communication sessions; determining an averageloss rate in accordance with the loss rates of each communicationsession; communicating a loss rate of the communication session and theaverage loss rate to the other of the two endpoints to permit the otherof the two endpoints to adjust its encoding rate. Segmenting andpackaging the data packet can further comprise modifying a header of thedata packet and appending modified headers to each of the encoded datasegments. Modifying the headers can comprise, for example, modifying asequence number of a TCP header. Identifying information, such as aserial number, for each segment derived from a given data packet canalso be added to each segment.

In a further aspect, there is provided a method of setting an encodingrate for encoding data for accelerated data communication across anunreliable network. The method comprises establishing an encoded channelfor each of a plurality of communication sessions, and monitoring lossrates of each communication session. An average loss rate is alsodetermined in accordance with the loss rates of each communicationsession. The loss rate of a communication session and the average lossrate are communicated to a respective endpoint to permit the endpoint toadjust its encoding rate to reduce its respective loss rate. Monitoringthe loss rates can comprise observing loss rates, and receiving reportedloss rates.

A further aspect provides a method for streaming video or audio data, orfor encoding unidirectional communication sessions, such as overReal-Time Streaming Protocol (RTSP) or between H.323 endpoints. Themethod comprises providing encoding components at a client and at aserver. A message destined to a default port is detected at the encodingcomponents, and parsed using deep packet analysis to determine a sessionidentification for the message. A reply to the message is then detectedat the encoding components, and parsed to determine communication portsallocated for use in respect of the communication session. Subsequentdata packets are then inspected to determine their originating anddestination ports. Each data packet having originating and destinationports that match the allocated communication ports is segmented andmarked to provide encoded data segments for transmission to the client.The data packet is decoded and reassembled, based on the receivedencoded data segments at the encoding component associated with theclient. In an embodiment, the deep packet analysis can be achieved usinga regex function.

Other aspects and features of the present invention will become apparentto those ordinarily skilled in the art upon review of the followingdescription of specific embodiments of the invention in conjunction withthe accompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of the present invention will now be described, by way ofexample only, with reference to the attached Figures, wherein:

FIG. 1 is a block diagram of an environment in which the invention maybe practiced;

FIG. 2 is a block diagram illustrating the components in a server usedin FIG.

FIG. 3 is a block diagram illustrating the components in another serverused in FIG. 1;

FIG. 4 is a flowchart illustrating the steps executed when first dataunits are received and transformed into second data units fortransmission to the transport network;

FIG. 5 is a flowchart illustrating the steps executed when second dataunits are received from the transport network and transformed into firstdata units for transmission to an end network;

FIG. 6 illustrates an exemplary system and a connection negotiationprotocol according to an embodiment of the present invention;

FIG. 7 illustrates a generic segmentation and encoding of a packetaccording to the present invention;

FIG. 8 shows an exemplary segmentation and encoding of a packetaccording to an embodiment of the present invention; and

FIG. 9 shows an environment in which loss statistics can be determined.

DETAILED DESCRIPTION

Referring to FIG. 1, a block diagram of an environment in which theinvention may be practiced is illustrated. A first endpoint 10communicates, through a network 20, with a second endpoint 30. The firstendpoint 10 and the network 20 communicate through an encoding/decodingcomponent 40, while the network 20 communicates with the second endpoint30 through an encoding/decoding component 50. The encoding/decodingcomponents 40 and 50, hereafter referred to as encoding components, canbe resident at the endpoints, or in an intermediate device, such as aserver. The first and second endpoints 10 and 30 can be terminals, suchas personal computers connected through a modem, local or wide-areanetworks, or other devices or systems having access to the network 20.The network 20 can be, for example, the Internet or other communicationsnetwork.

As used herein, a data unit is any unit of data that can be used totransmit data digitally over a network. Such data units can take theform of packets, cells, frames, or any other such units, provided thedata is encapsulated within the unit, or carried as a payload. The termdata unit is applicable to any and all packets and frames that implementspecific protocols, standards, or transmission schemes. Typically, aheader, carrying routing, control and identification information, isadded to the data payload.

The present system provides a means for insulating the endpoints fromthe vagaries of the network 20. The encoding components 40 and 50 areprovided with means to insulate the endpoints 10 and 30 from the network20 by handling the encoding and decoding of data units, and theirtransmission through the network 20. The endpoints 10 and 30 cancommunicate using any protocol, as can the encoding components 40 and50. The encoding components 40 and 50 receive original data units in oneprotocol from the endpoints 10 and 30, and encode the original dataunits by subdividing them into preferably smaller data units, creatingextra data units that can be used to recreate or reconstruct theoriginal data units in the event that some of the data units transmittedthrough the transport network are lost, and repackaging the subdividedand extra data units according to the present protocol prior totransmitting them through the transport network.

Once the data units transmitted through the transport network 20 arereceived at the encoding component associated with the far endpoint, theoriginal data units from the originating endpoint are recreated orreconstructed. This recreation or reconstruction can be done byreordering the received data units, if necessary, and, if some dataunits were lost during transmission, using the extra data units torecreate missing data units. In the event the extra data units receivedare insufficient to recreate the original data units, the receivingencoding component can optionally request a re-transmission of the dataunits previously sent.

For ease of explanation, data units originating from or received at theendpoints will be referred to as first data units, or packets, and asbeing of a first type of data unit. Data units being transmitted acrossand/or received from the transport network will be referred to as seconddata units, or segments and as being of a second type of data unit. Thesecond data units are also referred to as encoded data units.

FIG. 2 shows an exemplary embodiment of modules necessary to implementthe present invention within encoding component 40, and their respectivedata flows. The modules can be resident in a single device, or can bedistributed amongst several devices. As can be seen, encoding component40 has a first interface 60, a second interface 70, a reassembly module80, and a segmentation module 90. The first interface 60 sends andreceives first data units to and from an endpoint 10. The secondinterface 70 of the server 40 sends and receives second data units toand from the transport network 20.

The reassembly module 80 receives second data units from the secondinterface 70 and produces first data units for transmission to the firstnetwork 10 by way of the first interface 60. The segmentation module 90,on the other hand, receives first data units from the first interface 60and produces second data units for transmission to the transport network20 by way of the second interface 70.

Once the second data units have been transmitted through the transportnetwork, they are received by the encoding component at the otherendpoint. To illustrate this, FIG. 3 illustrates an exemplary embodimentof the modules and data flow of encoding component 50, whichcommunicates with the transport network and endpoint 30.

The modules in the encoding component 50 are the same as those inencoding component 40 and, in fact, have the same functions. The secondinterface 70A in encoding component 50 also communicates with thetransport network and sends and receives second data units. The firstinterface 60A also communicates with an endpoint (in this case theendpoint 30) and sends and receives first data units. The reassemblymodule 80A receives second data units and produces first data unitswhile the segmentation module 90A receives first data units and producessecond data units.

As noted above, first data units are the data units used by the endnetworks, while second data units are used by the transport network andthe encoding components 40, 50 when transmitting data to and from eachother. The second data units are derived from the first data units. Thepayload of the first data units can be divided into smaller units andeach smaller unit can be the payload in a second data unit. As such,each second data unit can be smaller than the original first data unitfrom which it was derived. As an example, a 10 kB first data unit may besubdivided into five 2 kB units. These may be the payload of five seconddata units, each of which may be smaller than 10 kB. This function ofcreating second data units from first data units is accomplished by thesegmentation modules 90, 90A.

To assist in recreating the original first data unit from which thesecond data units were derived from, the segmentation module alsocreates extra second data units. These extra second data units can bederived from the first and second data units. The extra second dataunits assist the reassembly modules 80, 80A in recreating orreassembling the original first data unit in the event one or moresecond data units are lost during their transmission through thetransport network.

The extra second data units can take many forms. In perhaps the simplestembodiment, the extra second data units are merely copies of selectedsecond data units previously sent. As an example, if a first data unitis divided or segmented into four second data units (e.g. DU1, DU2, DU3,DU4), then the extra second data units could be copies of DU2 and DU3.As such, if DU2 or DU3 are lost during the transmission, then theoriginal first data unit can still be recreated. The number andidentification of the second data units that are duplicated can bepredetermined, or left to the discretion of the system administrator.More redundancy can be built in to the system by including moreduplicate second data units, or vice versa for less redundancy,depending on the actual or expected degree of loss in the network 20. Inthe simplest case, all the second data units can be duplicated to ensurethat, in essence, two copies of each second data unit are sent to thedestination encoding component.

Parity data units can also be used as the second extra data units. As iswell known in the art, a parity data unit can be created using the XORfunction. The bits of the different second data units created from theoriginal first data unit can be XOR'd to result in bit values which canbe stored in an extra second data unit. If any one of the second dataunits (not including the extra second data unit) is lost duringtransmission, the other received second data units and the extra seconddata unit can be used to recreate the lost second data unit. Performingan XOR function on the received second data units and the extra seconddata unit will recreate the missing second data unit.

It should be noted that the extra second data units may be encoded usingother erasure correcting codes. As an example, if n second data unitsare generated for a single first data unit, m extra second data unitsmay be generated to allow the lost second data units to be recreated. Asnoted above, the m extra second data units may be viewed as “redundant”second data units and, if mere duplication is used, m≦n with completeduplication being achieved at m=n. However, if erasure correcting codesare used, with m=2, it is possible to encode the redundant informationin such a way that any two second data units can be lost and thereassembly modules can still reconstruct the lost second data units.Well-known methods and coding techniques such as Reed-Solomon, ForwardErasure Correction techniques, and Bose-Chaudhuri-Hochquenghem (BCH)codes, and a multitude of others may be used.

While the extra second data units should assist in counteracting theeffects of losing some second data units, losing too many second dataunits cannot be completely compensated for. As such, losing a number ofsecond data units past a threshold level can optionally cause thereassembly modules to request a re-transmission of a package or group ofsecond data units. As an example, if the extra second data units canrecover from a 25% loss of data units and there are four second dataunits generated from a single first data unit, then the loss of a singlesecond data unit would not trigger a re-transmission request. However,with the loss of two second data units (i.e. a 50% loss) the reassemblymodule could request a re-transmission. If re-transmission is enabled,the re-transmission threshold is ideally related to the error orloss-correcting capability of the coding used for the extra or redundantsecond data units. The reassembly modules can keep track of the numberof second data units received for each first data unit that has beensegmented, as the reassembly modules will need to properly sequence thepayloads of the second data units.

As can be noted from the above, the reassembly modules 80 and 80A decodeand reassemble the second data units received to form the original firstdata units. The second and extra second data units received are trackedto determine if a sufficient number have been received to recreate theoriginal first data unit. If a sufficient number have not been received,retransmission can optionally be requested. If some second data unitshave been lost, then the reassembly modules can recreate or reconstructthe missing second data units. As noted above, this process depends uponthe coding used and the overall strategy employed. Such decoding anderror correction processes are well known to those versed in this art.

Once the required number of second data units has been received, theirpayloads are extracted and used to reconstruct the original first dataunit from which the second data units were derived. This may be assimple as concatenating the payloads of the second data units to resultin the reconstructed first data unit. However, as noted above regardingthe decoding, the reconstruction process will depend upon the processused to segment or divide the original first data unit. Once theoriginal first data unit is reconstructed, it can be forwarded to theappropriate interface communicating with the receiving endpoint.

Regarding the segmentation modules, these modules perform the task ofsegmenting or dividing the first data units and “repackaging” thesegments into second data units. The segmentation modules also encodethe extra second data units as discussed above. The second data units,both those derived from the first data unit and the extra second dataunits, are then passed on to the interface module, which communicateswith the transport network. To facilitate the optional re-transmissionof second data units, the segmentation module can also buffer seconddata units. As an example, if five first data units have been segmentedinto twenty second data units and five extra second data units, thesegmentation module can buffer the last three sets of second data unitscorresponding to the last three first data units encoded. Thus, twelvesecond data units and three extra second data units would be buffered bythe segmentation module.

The segmentation module can also be configured to transmit second dataunits in an interleaved manner, to spread the risk of losing multiplesecond data units across different segmented first data units. Thus,instead of sequentially sending groups of second data units such thateach group corresponds to a single first data unit, second data unitsfrom different first data units can be interleaved with one another. Toillustrate, it can be assumed that first data units A, B, and C arerespectively segmented into second data units DU-A1, DU-A2, DU-A3;DU-B1, DU-B2, DU-B3; DU-C1, DU-C2, and DU-C3. Instead of sending thesesecond data units grouped according to their respective first dataunits, they can be interleaved. If second data units are sent in groupsof three data units, then the first group can be DU-A1, DU-B1, andDU-C1. Another group can be DU-A2, DU-B2, and DU-C2, and so on. Usingthis scheme, if a group is lost, then a whole first data unit is notlost—only one third of the three first data units is lost. Depending onthe coding and strategy employed, this type of loss may be recoverable.

An exemplary method according to the present invention, as implementedin one of encoding components 40 and 50, is shown in FIG. 4. The processbegins, with step 100, by receiving a first data unit from the sourceendpoint. After being received, the first data unit is then divided orsegmented (step 110) and the segments are packaged into second dataunits (step 120). Once the second data units are created, the extra orredundant second data units are encoded and created (step 130). Thesecond data units can then be optionally buffered (step 140) andtransmitted to the transport network (step 150). The method then returnsto step 100 via connector A. If re-transmission is enabled, an optionalcheck for a re-transmission request can be made (step 160)asynchronously. If such a request is received, then the decision flowreturns to step 150, and the requested second data units, previouslybuffered in optional step 140, can be transmitted.

FIG. 5 shows an exemplary embodiment of steps executed by an encodingcomponent receiving second data units from the transport network. Theprocess begins at step 180 as the server receives second data units fromthe transport network. Decision 190 then determines if all the seconddata units have been received to reconstruct the first data unit fromwhich the second data units were derived. If all the second data unitshave been received, then the original first data unit is recreated atstep 200. Once the first data unit have been recreated, the recreateddata unit is transmitted to the destination endpoint (step 205) and thecontrol flow moves back to step 180 by way of connector D.

Returning to decision 190, if not all the second data units have beenreceived, then a decision is made to determine if extra second dataunits have been received (step 220). If no extra second data units havebeen received, re-transmission can be optionally requested (step 230).After the optional re-transmission request, the control flow returns tostep 180 by way of connector D. If extra second data units have beenreceived, decision 240 determines if sufficient extra second data unitsand second data units have been received to reconstruct the originalfirst data unit. If an insufficient number have been received, theoriginal packet can be dropped, or, optionally, the control flow canreturn, as indicated by connector C, to step 230: requesting are-transmission. If a sufficient number of second data units and extrasecond data units have been received, then the extra second data unitscan be used to recreate or reconstruct the missing second data units(step 260). Connector B then returns the control flow to step 200.

Some specific examples of implementation will aid in understanding theoperation of the present system and method. FIG. 6 shows an exemplarysystem having endpoints A and B. Endpoint A communicates with a network300, such as the Internet, through an encoding component 302. Endpoint Bis also in communication with the network 300 through an encodingcomponent 304. Encoding components 302 and 304 include the interfaces,segmentation and reassembly modules described in relation to FIGS. 2 and3, and can be implemented wholly in software or can be implemented aspre-programmed hardware units, other related software, or as acombination of hardware and software components. An Ethernet, or othersuitable connection, can be used to connect each endpoint to itsrespective encoding component.

For the purposes of this example, it is assumed that a bidirectionalcommunication is occurring between endpoints A and B, and that endpointA initiates the communication. The present communication protocol isinvisible to both endpoints A and B; all functionality resides in theencoding components 302 and 304. To set up a session between endpoints Aand B, and to determine if both endpoints are associated with encodingcomponents to permit communication in accordance with the presentprotocol, the connection negotiation protocol illustrated in FIG. 6 canbe used. Endpoint A sends a packet P destined to endpoint B. The packetP and its destination are detected or noticed (306) by encodingcomponent 302, and encoding component 302 stores information uniquelyidentifying the communication session. Packet P is also detected ornoticed (308) by encoding component 304. Encoding component 304 storesinformation uniquely identifying the communication session (310) relatedto the packet and sends the packet to endpoint B. When endpoint B sendsa reply packet R to endpoint A, the reply packet R is intercepted byencoding component 304, matched with the previously stored informationidentifying the communication session and marked (312). The informationuniquely identifying the communication session can be, for example, thesource IP address, the destination IP address, the protocol containedwithin the IP packet (e.g. UDP or TCP), and the source and destinationports. For Ethernet frames, the VLAN ID can also be used.

The marked packet R^(m) is used to signal to encoding component 302 thatencoding component 304 is capable of receiving and sending packetssegmented and encoded according to the present invention. Marking thepacket can consist of, for example, setting an option in the IP headerof the packet, and/or setting the IP identification field to a knownvalue. Routers and other devices in the public network 300 may leave theIP identification field unchanged during transmission. Other suitablemarking or signaling schemes, such as setting the IP address flag in thetimestamp, can be used, provided that they are preferablynon-destructive, and non-disruptive to devices that are not capable ofcommunication in accordance with the present protocol.

Encoding component 304 then forwards the marked packet R^(m) to endpointA, via the public network 300. The marked packet R^(m) is detected byencoding component 302, which updates the previously stored informationidentifying the communication session (316), and sends the packet toendpoint A. The encoding component 302 can optionally remove the markprior to forwarding the packet to endpoint A. When endpoint A sendsanother packet P₂ destined to endpoint B, encoding component 302 matches(318) the packet P₂ with the previously stored information identifyingthe communication session. Recognizing that endpoint B is provided withan encoding component enabled to communicate in accordance with thepresent protocol, encoding component 302 sends a “hello” message inaddition to forwarding the packet P₂.

On receipt of the “hello” message from encoding component 302, encodingcomponent 304 replies with a “hello” reply. Encoding component 302 thensends a reply acknowledgment (“reply ack”) to encoding component 304,and begins to segment and encode data packets destined for endpoint Busing the present protocol. When component 304 receives the replyacknowledgment from component 302, it also begins to segment and encodedata packets destined for endpoint A to provide the second data unitspreviously described. The encoded channel between encoding component 302and 304 is thus successfully automatically detected and negotiated. Theencoded channel can be used to carry both data and control information.Once an encoded channel has been negotiated between two encodingcomponents enabled to use the present protocol, segmented and/or encodedmessages can now be sent and received. The encoded channel remainsactive until a predetermined timeout period has elapsed during which theencoding components fail to receive any further packets. Both sides thentear down the encoded channel. Other methods for negotiating the encodedchannel between two endpoints are also contemplated. For example, theencoded channel can be negotiated through a pre-existing control channelbetween the endpoints to the communication.

It should be noted that all communication between the endpoints and thecomponents 302 and 304 occurs over the established or existingcommunication channel. The channel can implement known communicationprotocols, such as Universal Datagram Protocol (UDP) and TransmissionControl Protocol (TCP), both over IP. If the connection is a UDPconnection, messages according to the present invention are inserteddirectly into the UDP data payload.

If sending data over an existing TCP connection, the original TCP headercan be appended to each segment, with the sequence numbers modified.Thus, the source port and destination ports remain the same. The firstsegment is given the sequence number of the original packet, butsubsequent segments are provided with new sequence numbers. In apresently preferred embodiment, an encoded or extra segment re-uses asequence number of one of its related segments. This permits the extrasegment to pass through firewalls in the same manner as would are-transmitted packet. The data offset and checksum remain unchanged,but the flags, or control bits, are modified for all but the initialsegment. For non-segmented messages (i.e. control messages), theremaining message bytes immediately follow the modified TCP header. Forsegmented messages, a segment payload follows the modified TCP header toprovide, for example, identifying information, such as a serial number,to identify a segment and its relation to other segments, and to enablereassembly of the original packet. The data payload of the segment thenfollows.

As will be appreciated, a packet marked or created as described abovewill pass unchallenged through firewalls and Network Address Translation(NAT) translators. Effectively, the encoded channel establishes acontrol channel between the encoding components 302 and 304, and packetscan pass from either end without being recognized or challenged by anyintermediate component, such as a firewall or NAT.

Segmentation and encoding of a packet according to an embodiment of thepresent invention will now be described with reference to FIG. 7. Tosimplify the discussion, headers have been omitted from the originalpacket and the segmented packets. An original data payload 400 isreceived at an encoding component according to the present invention.The original data payload has x bytes, and is segmented into n segments402. Where n is chosen as an integer factor of x, each of the n segmentswill have x/n bytes, as shown. In addition, m additional segments arecreated. In the example shown in FIG. 7, m=1 and the additional or extrapacket 404 is a parity segment created by applying an XOR function toone of the n segments.

It may not always be possible or desirable to divide the original datapayload 400 into even segments. For example, it may be necessary to padthe last segment to ensure all segments are of equal length where n isnot a factor of x. For example, if x=17 and n=2, the nearest integervalue to x/n is 9. Segment sizes that are factors of 4 or 8 aregenerally preferred, thus the segment size in this case is chosen to bethe next factor of 4 greater than, or equal to x/n (e.g. 12 bytes). Asshown in FIG. 8, the original 17 byte data payload 410 is segmented intotwo 12 byte segment payloads 412 and 414. Segment payload 412 containsthe first 12 bytes of the original data payload 410, and segment payload414 contains the remaining 5 bytes from the original data payload 410optionally padded out to 12 bytes. A further extra segment 416, which isa parity segment of segment 412, forms the final segment in thesequence. It should be noted that all the segments related to a singleoriginal packet or frame have the same serial number to permit theiridentification and reassembly at the receiving end.

The encoding rate is determined by both n and m. The encoding rate canbe set to predetermined values (e.g. n=2, m=1 as shown in FIG. 8), orcan be adjusted based on observed and/or reported network performancefor all encoded channels terminating at an encoding component associatedwith a given endpoint. One method of determining network performancewill now be described in relation to FIG. 9. In FIG. 9, endpoint A iscommunicating with endpoints B, C and D over a public network 440. Eachof the endpoints is enabled to communicate according to the presentprotocol. The encoding component (not shown) associated with endpoint Acontinually monitors the losses it is experiencing in receiving segmentsfrom each of the other endpoints. The encoding component can monitorsuch losses by, for example, maintaining a count of the number ofsegments it has failed to receive, or by counting the number of resendrequests it sends to each of the other endpoints during their respectivesessions. A resend request can be sent by endpoint A whenever it detectsexcess missing segments in a sequence. Endpoint A can also receivedetails of observed network performance from endpoints B, C, and D.Applying such methods, endpoint A determines that the connections A-Band A-C are good, and are experiencing little loss. However, thecollected performance statistics show that the connection A-D is lossy,and endpoint A is experiencing high loss from D. This likely means thatthere is a local pocket of loss 442 somewhere between A and D. EndpointA reports to D that it is experiencing high loss from D, but low loss onaverage. This allows D to decrease or increase its encoding rate (i.e.decrease or increase n and/or m) to improve the chance that, despite thelossy channel, packets can be recovered at endpoint A from the receivedsegments.

The examples described above generally relate to bidirectionalcommunications between endpoints, where negotiation of the encodedchannel is feasible and desirable. However, the present invention canalso be used in substantially unidirectional, or streaming, applicationsto accelerate their performance, and in other applications wherenegotiating the connection between the encoding components isimpractical or otherwise undesirale. In such applications, nonegotiation is required between the encoding components associated witheach endpoint. The encoded channel is established by recognizing callsignaling messages, and subsequent deep packet analysis permits messagesrelated to the communication session to be recognized.

For example, the encoding/decoding components of the present inventioncan be used to take advantage of the stateful nature of Real-TimeStreaming Protocol (RTSP) to set up and monitor a connection forstreaming. The default port for RTSP commands is port 554. Therefore,the encoding components of the present invention can analyze packetheaders to determine if they are destined to, or originate from, theRTSP default port, and thereby identify RTSP packets. If a RTSP messageis detected, the message can be parsed to determine if it contains aSETUP request, a SETUP response, a TEARDOWN request, or a general RTSPresponse. A SETUP request from a user contains the media stream URL anda local port for receiving RTP data (audio or video). The RTSP serverreply confirms the chosen parameters, and provides the server's chosenports. By parsing the reply from the RTSP server, the encodingcomponents can determine the RTSP session identification assigned to thedata stream, the RTSP sequence number for the message, and the RTP portsthat have been allocated for the session by the user terminal and theRTSP server. In this way, an encoded channel for streaming can be set upbetween the encoding components. Subsequent data units between theclient and server can then be analyzed, such as by deep packet analysis.If the ports match those set in the SETUP reply, the message can beintercepted for segmentation and encoding, or decoding and reassembly,as described above, without any negotiation to set up the encodedchannel.

Similarly, for H.323, the encoding components can analyze packets formessages indicating an H.323 call is being set up. For example, theencoding components can detect and do a deep packet analysis onH.225/Q.931 call setup messages and/or H.245 negotiation and path setupmessages to identify called and caller data ports that will be used forthe associated H.323 session. An encoded channel according to thepresent protocol can then be set up to intercept and encode the dataflow as described above.

In the following description, for purposes of explanation, numerousdetails are set forth in order to provide a thorough understanding ofthe present invention. However, it will be apparent to one skilled inthe art that these specific details are not required in order topractice the present invention. In other instances, well-knownelectrical structures and circuits are shown in block diagram form inorder not to obscure the present invention. For example, specificdetails are not provided as to whether the embodiments of the inventiondescribed herein are implemented as a software routine, hardwarecircuit, firmware, or a combination thereof.

Embodiments of the invention may be represented as a software productstored in a machine-readable medium (also referred to as acomputer-readable medium, a processor-readable medium, or a computerusable medium having a computer readable program code embodied therein).The machine-readable medium may be any suitable tangible medium,including magnetic, optical, or electrical storage medium including adiskette, compact disk read only memory (CD-ROM), memory device(volatile or non-volatile), or similar storage mechanism. Themachine-readable medium may contain various sets of instructions, codesequences, configuration information, or other data, which, whenexecuted, cause a processor to perform steps in a method according to anembodiment of the invention. Those of ordinary skill in the art willappreciate that other instructions and operations necessary to implementthe described invention may also be stored on the machine-readablemedium. Software running from the machine readable medium may interfacewith circuitry to perform the described tasks.

The above-described embodiments of the present invention are intended tobe examples only. Alterations, modifications and variations may beeffected to the particular embodiments by those of skill in the artwithout departing from the scope of the invention, which is definedsolely by the claims appended hereto.

What is claimed is:
 1. A method of accelerating data communicationsbetween any of a plurality of endpoints over an unreliable IP network;comprising: providing encoding components associated with each of twoendpoints to a communication; establishing a communication channelbetween the encoding components for a communication session between theendpoints; intercepting a first layer 3 or above data packet related tothe communication at one of the encoding components; segmenting andpackaging said first layer 3 or above data packet to provide two or moresecond layer 3 or above data segments for transmission to the other ofthe encoding components; transmitting the second layer 3 or above datasegments and at least one extra second layer 3 or above segment to theother of the encoding components over the communication channel;decoding and reassembling the first layer 3 or above data packet at theother of the encoding components based on the received second layer 3 orabove data segments; and transmitting the reassembled first layer 3 orabove data packet from the other encoding components to its respectiveendpoint, wherein said segmenting and packaging further comprises:monitoring retransmission request metrics for each of a plurality ofcommunication sessions; determining an average retransmission requestmetrics in accordance with the retransmission request metrics of eachcommunication session; and communicating a retransmission requestmetrics of the communication session and the average retransmissionrequest metrics to the other of the two endpoints to permit the other ofthe two endpoints to adjust its encoding rate.
 2. The method of claim 1,wherein a number of second layer 3 or above data segments fortransmission and a number of extra second layer 3 or above segment aredetermined based on encoding parameters.
 3. The method of claim 1,wherein establishing the communication channel comprises: detecting alayer 3 or above data packet originating from a first of the twoendpoints and destined to the other of the two endpoints; storinginformation uniquely identifying the communication session; marking thelayer 3 or above data packet destined to the other endpoint to indicatethat the first endpoint is enabled to segment and encode layer 3 orabove data packets according to a protocol known to both encodingcomponents; forwarding the marked messages to the other endpoint; andexchanging control messages to establish the communication channelbetween the encoding components.
 4. The method of claim 3, whereinmarking comprises setting an option in an Internet Protocol header ofsaid layer 3 or above data packets.
 5. The method of claim 3, whereinmarking comprises setting an identification field of said layer 3 orabove data packets to a known value.
 6. The method of claim 3, furthercomprising tearing down the communication channel if no further layer 3or above packets are transmitted within a predetermined timeout period.7. The method of claim 3, wherein storing information uniquelyidentifying the communication session comprises storing a source IPaddress, a destination IP address, a protocol contained within the layer3 or above packet, and source and destination ports.
 8. The method ofclaim 1, wherein establishing the communication channel comprises:detecting a layer 3 or above data packet originating from a first of thetwo endpoints and destined to the other of the two endpoints; storinginformation uniquely identifying the communication session; determiningif the layer 3 or above data packet is related to the communicationsession and has been marked to indicate that the other endpoint isenabled to segment and encode the layer 3 or above data packetsaccording to a protocol known to both encoding components; transmittingcontrol messages to establish the communication channel between theencoding components.
 9. The method of claim 1, wherein establishing thecommunication channel comprises: detecting control messages of a knownprotocol establishing said communication session between two endpoints,the control messages including an identification of originating anddestination ports; and creating the communication channel in response tothe detected control messages.
 10. The method of claim 9, wherein thecommunication session is a Real Time Streaming Protocol (RTSP) session.11. The method of claim 9, wherein the communication session is a H.323protocol session.
 12. The method of claim 1, wherein establishing thecommunication channel comprises exchanging information over apre-existing control channel established between the two endpoints. 13.The method of claim 1, wherein segmenting and packaging the layer 3 orabove data packet comprises segmenting the layer 3 or above data packetinto data segments in accordance with a predetermined encoding rate. 14.The method of claim 1, wherein segmenting and packaging the first layer3 or above data packet comprises modifying a header of the layer 3 orabove data packet and appending modified headers to each of the secondlayer 3 or above data segments.
 15. The method of claim 14, whereinmodifying the header comprises modifying a sequence number of a TCPheader.
 16. The method of claim 14, wherein modifying the headercomprises modifying TCP header flags.
 17. The method of claim 14,wherein modifying the header comprises modifying the urgent pointer in aTCP header.
 18. The method of claim 1, wherein segmenting and packagingthe first layer 3 or above data packet comprises adding identifyinginformation to each layer 3 or above data segment.
 19. The method ofclaim 1, wherein said at least one extra second segment includes aparity code.
 20. The method of claim 1, wherein said at least one extrasecond segment is a copy of said encoded data segments.
 21. The methodof claim 1, wherein said second data segments are of same size.
 22. Themethod of claim 1, wherein the number of said second data segments is amultiple of
 4. 23. An apparatus for accelerating data communicationsbetween two endpoints over an unreliable IP network, the apparatuscomprising: an endpoint interface in communication with a firstendpoint, the endpoint interface intercepting a first data packetreceived from the first endpoint, the first data packet related to acommunication session established between the first endpoint and asecond endpoint; a segmentation module coupled to the endpoint interfaceand a network interface, the segmentation module receiving the firstdata packet from the endpoint interface and segmenting and packaging thefirst data packet to provide a first plurality of data segments to thenetwork interface, the segmentation module also providing a first extrasegment to the network interface, wherein the segmentation modulemonitors retransmission request metrics for the communication sessionand determines an average retransmission request metrics in accordancewith the retransmission request metrics of a plurality of communicationsessions, the segmentation module communicating the retransmissionrequest metrics of the communication session and the averageretransmission request metrics to the first endpoint to permit the firstendpoint to adjust its encoding rate; the network interface transmittingthe first plurality of data segments and the first extra segment overthe unreliable IP network to the second endpoint, the second endpoint incommunication with the network interface over the unreliable IP network;the network interface receiving a second plurality of data segments anda second extra segment from the unreliable IP network, the secondplurality of data segments and the second extra segment associated withthe communication session; a reassembly module coupled to the networkinterface and the endpoint interface, the reassembly module receivingthe second plurality of data segments and the second extra segment fromthe network interface and decoding and reassembling a second data packetbased on the received second plurality of data segments and the secondextra segment; the endpoint interface receiving the second data packetfrom the reassembly module to transmit it to the first endpoint; whereinthe first data packet, the second data packet, the first plurality ofdata segments, the second plurality of data segments, the first extrasegment, and the second extra segment all use layer 3 or aboveprotocols.
 24. The apparatus of claim 23, wherein the communicationsession is established by exchanging information over a pre-existingcontrol channel established between the first endpoint and the secondendpoint.
 25. The apparatus of claim 23, wherein the segmentation modulesegments and packages the first data packet into the first plurality ofdata segments using a predetermined encoding rate.
 26. The apparatus ofclaim 23, wherein the segmentation module modifies a header of the firstdata packet and appends modified headers to each of the first pluralityof data segments.
 27. The apparatus of claim 23, wherein segmentationmodule adds identifying information to each of the first plurality ofdata segments.
 28. The apparatus of claim 23, wherein the reassemblymodule generates retransmission requests for the second plurality ofdata segments when it is unable to decode and reassemble the second datapacket due to errors resulting in lost segments of the second pluralityof data segments or the second extra segment.